Summary

Adds RUSHSTACK_CLI_IGNORED_PARAMETER_NAMES environment variable to forward the parameterNamesToIgnore operation setting from rush-project.json to child processes during phased command execution. The environment variable name is exported as a public constant for use by consumers.

Details

Implementation:

• Created IgnoredParametersPlugin that taps the createEnvironmentForOperation hook
• Reads parameterNamesToIgnore directly from operation.settings (raw configuration value, not CLI-affected values)
• Sets RUSHSTACK_CLI_IGNORED_PARAMETER_NAMES with JSON-stringified array when defined (following ts-command-line convention for list-type parameters)
• Exported the environment variable name as RUSHSTACK_CLI_IGNORED_PARAMETER_NAMES_ENV_VAR constant with literal type annotation for external use
• Integrated into PhasedScriptAction alongside other standard plugins

Design:

• Follows pattern established by NodeDiagnosticDirPlugin
• Naming consistent with existing RUSHSTACK_FILE_ERROR_BASE_FOLDER convention
• Only sets environment variable when configuration explicitly defines ignored parameters
• Environment variable name exported as public constant with literal type to avoid hardcoded strings in consuming code
• Uses JSON.stringify() to encode array values, following the ts-command-line convention for passing list-type parameters via environment variables (handles special characters like commas correctly)

Example:

Given a rush-project.json with:

{
  "operationSettings": [
    {
      "operationName": "build",
      "parameterNamesToIgnore": ["--verbose", "--production"]
    }
  ]
}

Child processes will receive:

RUSHSTACK_CLI_IGNORED_PARAMETER_NAMES='["--verbose","--production"]'

Consumers can reference the environment variable name using:

import { RUSHSTACK_CLI_IGNORED_PARAMETER_NAMES_ENV_VAR } from '@microsoft/rush-lib';

How it was tested

Added unit tests verifying:

• Environment variable set correctly when parameterNamesToIgnore is specified
• Environment variable not set when parameterNamesToIgnore is absent
• Correct values forwarded for different project configurations (JSON-stringified arrays)
• Tests use the exported constant to avoid hardcoded strings

All tests pass. No regressions in existing test suite.

Impacted documentation

None. This is an internal implementation detail for plugin authors.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.